home *** CD-ROM | disk | FTP | other *** search
-
-
-
-
-
- Upgrade Instructions for Version 2.00
-
-
- This file is *ONLY* for users upgrading from TODAYS.PRG
- version 1.99 to version 2.00. If you are a new user, or are
- upgrading from a release prior to 1.99, *PLEASE* read the
- documentation on how to set up TODAYS.PRG. There have been a
- LARGE number of changes since version 1.98!
-
- Changes to TODAYS.LNG:
-
- Please replace your current TODAYS.LNG file with the one
- included in the distribution package. There have been a number of
- changes and enhancements. The program will abort if you fail to
- do so.
-
- Changes to TODAYS.INF:
-
- Line 5 has been deleted! Please make this change BEFORE you
- do anything else! Simply load TODAYS.INF into your favorite Text
- Editor/Word Processor and delete the line out completely, pulling
- up the rest of the lines in the file. For those of you who still
- want/need to use a 'header', please see the new code (%FEXT) in
- the TODAYRPT.FMT file.
-
- Next, insert a line in between the Wrap Value and the
- Carridge return code making a new line 8 and pushing the rest of
- the lines down. On this line, place a number between 0 and 32767.
- This number will be for the number of spaces from the left edge of
- the screen to where you want the text to start should a line be
- wraped around. (It'll have no effect if the lenght of the text is
- less then your Wrap Value.)
-
- After making those changes, your file should be like the one
- shown below, adjusting for your individual systems of course.
-
- line# Meaning:
- ----- -------------------------------------------------------
- 1 Location of TODAY.mmm files
- 2 Extenders of additional TODAY.xxx files
- 3 Location of alternate file (1 big file)
- 4 Where to send the output to
- 5 What to do if there's already a existing file (append or
- replace)
- 6 Age value
- 7 Wrap value
- 8 Second line indents on wraped lines (# of spaces)
- 9 Carridge return codes (3 digits each character
- 10 Sort or NoSort of output dates.
- 11 Show where the data came from (which file)
- 12 Maximum number of items to collect
-
-
-
-
-
-
-
-
- - 1 -
-
-
-
-
-
-
- To allow you to set your own 'seperator' that goes between
- the year and the text, a new line, number 13, now allows you to
- 'define' that. This is the dash that used to be hard coded into
- the program. A space will be added to the text on this line
- unless you enclose the text you want in quote marks ("). Examples:
-
- If line 13 is:
- - ; String to put between the year and the text
- you will get:
- 1992 - Year of the Frog.
-
- If line 13 is:
- "-" ; String to put between the year and the text
- you will get:
- 1992-Year of the Frog.
-
- If line 13 is:
- <> ; String to put between the year and the text
- you will get:
- 1992 <> Year of the Frog.
-
- If line 13 is:
- "<>" ; String to put between the year and the text
- you will get:
- 1992<>Year of the Frog.
-
- In addition, to allow you to change the text color,
- background color or the font that's used to do the text on the
- line, 2 more optional lines have been added to the TODAYS.INF
- file.
-
- Line 14 sets the text before the year, and line 15 sets it
- before the text.
-
- You can also use line 13 to set the color before the prompt
- as well as for defining the prompt, so you can now control all
- three 'display' areas.
-
- NOTE: You do *not* have to use lines 13, 14 and 15! You do
- not even have to have them in your TODAYS.INF file. These lines
- are for those users who want access to those areas to make
- whatever changes they want to them. TODAYS.PRG does not require
- your use of them!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 2 -
-
-
-
-
-
-
- Changes to TODAYS.RPT:
-
- MASSIVE CHANGES!!!!
-
- Your old report will no longer work! *ALL* the codes have
- been changed! Please see the TODAYRPT.FMT file included in the
- distribution package to determine what the new codes are and which
- ones you want to use. I think you'll like the new code structure,
- and find it's faster and easier to use, as well as being more
- flexable!
-
- To help 'convert' your old TODAYS.RPT file over to the new
- code structure, I wrote a program called TUPDATE.PRG which is
- included in the distribution package. It requires that the
- associated file "TUPDATE.MAP" be in the same directory as the
- program when you run it.
-
- A number of new codes have also been added to allow users
- more choice in the information they want displayed. Hopefully,
- this won't prove _too_ much for users to handle, as there are a
- few codes I still want to add.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 3 -
-
-
-
-
-
-
- Program fixes / enhancements:
-
- The program will now properly replace the output file when
- the user puts 'Replace' on line 5. Previous versions gave an
- error 24 when the user attempted to replace the existing output
- file.
-
- The rather offensive (to some users) 'reset screen' code that
- was sent out at the end of the TODAYS.PRG run has been deleted.
- Sorry 'bout that.
-
- The program can now handle function codes on the lines from
- the data files. ALL of the function codes are available in the
- lines plus 7 additional ones that will only work on the lines.
- Please see TODAYRPT.FMT for the codes and what can be done. This
- allows the user even greater flexability when designing their
- reports.
-
- I've been told that I was wrong about Stardates. I watched a
- couple of episodes of Star Trek: The Next Generation, and
- discovered that what I was told about them was indeed wrong:
- Stardates are FIVE digits long, not four. <sigh> A four digit
- Stardate only covers about 27 years, which doesn't make much sense
- when compared to Gregorian years. A five digit Stardate covers
- about 273 years. That doesn't make much sense to me either, but
- it does make more sense then a measly 27 years. For those of you
- would prefer the 4 digit version, you can 'trim' it with the
- function code (%FSTDNNR4%).
-
- The way the program handles the 'Pre-year' and 'Pre-text'
- strings (for color and/or font changing) has been changed due to
- the inclusion of the the function codes in the lines.
-
- Since the user can now put the year (or whatever) anywhere
- they want on the line, to use them only before the beginning of
- the line makes no sense. So the 'before year' string is now sent
- out before each function code in the lines, and the 'before text'
- string after the function code.
-
- This _may_ distort the line wrapping if you're using 'hidden'
- characters in your strings to change the colors and/or fonts so
- that it appears that the wrap function isn't working correctly.
- Remove the 'pre-year' and 'pre-text' strings, and you'll find that
- the wrap is indeed functioning correctly. The wrap function
- 'counts' those 'hidden characters' as characters, and it'd be a
- near impossible feat to 'fix' it so that it wraps the line without
- reguard to them. If someone knows of a way that I haven't thought
- of though, I'd be more then pleased to hear it!
-
-
-
-
-
-
-
-
-
-
-
- - 4 -
-
-
-
-
-
-
- When function codes are used in the lines, the lines are
- lined up differently then on lines without them.
-
- The lines, which used to always have the year first, were
- aligned so that all the years lined up, along with the year/text
- seperator string and the text on the line. With lines that have
- function codes on them, the lines are *not* lined up with the
- other lines. The left edge of the screen is where the text
- starts, and the year that is on the line is not displayed unless
- the user chooses to display it with a function call.
-
- With the addition of the function codes to the lines, the
- Anniverary 'group' is redundant and unnessesary, so I've deleted
- them. You may still use type $ codes for your anniversary events,
- however you'll have to add in a function call on the line
- (%FYERNSN%) to get the year with suffex out.
-
- Error reporting has changed. You'll still get the TODAYS.ERR
- file, but the errors are no longer shown on the screen as they are
- discovered. Instead the screen will display a message at the end
- of the program run requesting that the user look at the TODAYS.ERR
- file and then pause for 30 seconds before continuing on. Pressing
- any key durring the 30 second pause will abort the pause, and the
- program will continue on.
-
- An error in the TODAYS.RPT file will no longer cause the
- program to switch over to the 'built in default' report. Instead,
- the function call will not be converted, and the program will
- continue on to convert the other function codes in the file,
- ignoring the bad one.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 5 -
-
-